why is there {Raw,Safe,}Configparser in Python 3
Posted
by Tshepang
on Stack Overflow
See other posts from Stack Overflow
or by Tshepang
Published on 2010-05-17T11:47:12Z
Indexed on
2010/05/17
11:50 UTC
Read the original article
Hit count: 241
python
Am surprised there's 3 different forms: RawConfigParser, SafeConfigParser and ConfigParser. I read the differences but why isn't everyone using SafeConfigParser, since it seems, well, safe? I can understand that in the case for Python 2 that the other two were kept for backward compatibility.
© Stack Overflow or respective owner